Some files could not be transferred because their file names and/or paths could not be created on this computer, or they were not accessible on the local computer (eg. the file on the server was busy).

Usually, invalid file path problems only occur when files are being transferred between operating systems which support different character sets, and there is no automatic way to rename them.

The invalid file paths have been logged in a date-stamped error log file in the "Error_Logs" folder, with an entry for the "Remote file path" and an entry for the "Invalid local file path". The "Error_Logs" folder is located in the 'PC-Mac-Net FileShare 3.x' preferences folder.

To correct this problem, please change the name and/or path of the logged files on the local or remote computer. This may involve removing any exotic characters from the file name and/or path, or shortening the file name and/or path.

If a file was not available on the local computer, you should try transferring it again. The file may only have been unavailable for a short time, and may now be available.
